Skip to content

Sync dev from main - #332

Merged
aamoghS merged 1 commit into
devfrom
main
Aug 9, 2026
Merged

Sync dev from main#332
aamoghS merged 1 commit into
devfrom
main

Conversation

@aamoghS

@aamoghS aamoghS commented Aug 9, 2026

Copy link
Copy Markdown
Member

Brings dev up to date with main after #330.

The stack (#316, #318, #320, #323, #325) plus the follow-ups (#327, #328, #330) all landed directly on main, so dev needs the sync — otherwise anyone working off it is missing the membership decoupling, the judging fixes and the check-in fix that makes submission possible at all.

No new code here; this is a merge of commits already reviewed and merged on main.


Note

Low Risk
Merge-only sync with a trivial test fixture tweak; no runtime behavior changes in this diff.

Overview
This PR merges already-reviewed main commits into dev so branches stay aligned after work landed on main (#330 and related stacks). No new product logic appears in the diff.

The only visible change in the provided diff is in qr-checkin.test.ts: the clubEvent test helper drops pointsValue: 10, matching removal of event points from the API/schema elsewhere on main (membership decoupling). Test fixtures no longer model a field the product no longer uses.

Reviewed by Cursor Bugbot for commit 2a7fe0f. Bugbot is set up for automated code reviews on this repo. Configure here.

D4 removed event.points_value, but this club-event fixture still set it. Dead
data rather than a failure — the fixture is a plain object handed to a mock,
not typed against the schema — but it reads as though club events still carry
points, which is exactly the impression D4 set out to remove.

Verified: typecheck, 426 tests, lint --max-warnings 0, build.
@cursor

cursor Bot commented Aug 9, 2026

Copy link
Copy Markdown

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_799e0b3a-1552-4f7b-9626-a23018810da2)

@github-actions

github-actions Bot commented Aug 9, 2026

Copy link
Copy Markdown
Contributor

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None

@aamoghS
aamoghS merged commit b6225f7 into dev Aug 9, 2026
18 checks passed
@github-actions

github-actions Bot commented Aug 9, 2026

Copy link
Copy Markdown
Contributor

Visit the preview URL for this PR (updated for commit 2a7fe0f):

https://hacklytics2027--pr-332-i7h5vh7s.web.app

(expires Sun, 16 Aug 2026 03:17:23 GMT)

🔥 via Firebase Hosting GitHub Action 🌎

Sign: c48ba34db61581e25fe2978355160b5eefe0e83f

@greptile-apps

greptile-apps Bot commented Aug 9, 2026

Copy link
Copy Markdown

Greptile Summary

Removes the obsolete pointsValue property from the QR check-in test fixture to align it with the current event model.

  • Updates the mocked club event shape used by QR check-in tests.
  • Removes dead fixture data left behind after the corresponding event field was removed.

Confidence Score: 5/5

The PR appears safe to merge because the removed fixture property is no longer part of the event model and is not used by the tests.

The sole change removes dead data from an untyped mock fixture; current API and schema contracts do not include the property, and no check-in test relies on it.

Important Files Changed

Filename Overview
packages/api/src/.internal-tests/qr-checkin.test.ts Removes an obsolete, unused property from a plain mock event fixture without changing tested behavior.

Reviews (1): Last reviewed commit: "chore(tests): drop the last points fixtu..." | Re-trigger Greptile

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant